Repository navigation
Zapier v0.4.3: 25s request timeout with clear error (address verify Zap alert) - #2
Merged
Merged
Conversation
…iew W614ZP-P52RM, Nov 4 2026) - authentication.js: fallback label is 'API token' / 'API token missing' instead of 'BatchData API token' - test: fallbacks never include the app name - README/PUBLISH-CHECKLIST: review feedback and status
…+ live run, Nov 9 2026 - Billed session trigger: skip API call on dedupe population; sample load fetches 1; default take 5 - Billed searches (Find Properties, Permits, Investor Buy Box, Investor Properties) default take 1 - Batch Look Up / Batch Skip Trace: row-level Your Reference ID no longer dropped - 402 mapped to a clear insufficient-funds error - Skip Trace output fields now label the V3 record shape too - Remove no-op catch in hook subscribe; regression tests in test/signoff-0.4.2.test.js
…'s 30s task kill (address verify Zap alert, Nov 13 2026)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The hourly test Zap "Schedule Hourly Address Verification in BatchData" failed at 7:00pm and 8:00pm MST on Nov 12 (Zapier RequestIds 477a5a18-4144-4193-a875-d8ca7be86895 and b2dfc782-71ee-45a3-8a1c-d7d651b2fd70) with "Task timed out after 30.00 seconds". Zapier's HTTP log has no response for those runs, and ~20 other hourly runs succeeded, so
POST /api/v1/address/verifysometimes hung. Noz.requestin the app set a timeout, so Zapier killed the task with an error that doesn't say what happened.What changed (0.4.3)
beforeRequestsets a 25s timeout plus an AbortSignal that bounds the whole request, response body included. This covers every request.translateTimeoutswrapper on every perform and on the auth test turns a timeout into a clearTimeout(504) error that says to check billing before replaying. It does not auto-retry billed calls.Proof
npm test: 80 pass, 0 fail, 20 live tests skipped.zapier-platform validate: 0 errors and 0 publishing tasks. The only warning is the existing core 19.3.0 upgrade suggestion.